Initiation and support of video conferencing using instant messaging

ABSTRACT

A system and method for initiating and supporting network video conferences are disclosed. In accordance with the invention, one or more instant messaging enabled clients can initiate a video conference. At least a pair of client nodes communicate with each other via an instant messaging utility. An instant messaging server supports instant messages between the two client nodes. A second server, e.g., a video conferencing server, supports video conferences between video conference participants, a video conference being initiated between video conference participants in response to an instant message transmitted between the at least two client nodes.

RELATED APPLICATIONS

[0001] This application is based on U.S. Provisional Patent Application serial No. 60/250,695 filed on Dec. 1, 2000, the contents of which are incorporated herein in their entirety.

BACKGROUND OF THE INVENTION

[0002] Video conferencing via networks such as the Internet is becoming increasingly popular. Video conferences on the Internet are typically supported by a video conferencing server such as the Multipoint Conference Unit (MCU), manufactured, sold and licensed by First Virtual Communications, Inc. of Nashua, New Hampshire and Santa Clara, Calif. Participants in a video conference supported by such servers communicate via their local video conferencing client software over the Internet with the MCU, which provides the audio and/or video conferencing data to some or all of the participants. Typically, video conferences are initiated by one or more prospective participants communicating with the MCU, such as by visiting a dedicated website, to identify invitees to the conference. The MCU then initiates and supports the video conference by providing the appropriate conference data to the client associated with each of the identified participants through network links with each of the clients.

[0003] Instant messaging (IM) is becoming an increasingly popular utility on networks such as the Internet. Under instant messaging, IM clients on a network can communicate with each other via an IM server or messenger service of the network. The messenger service also typically provides a “presence” feature which permits IM clients to know the status of other clients on the network serviced by the messenger service. The status information for a client includes whether the client is online and available to receive instant messages from other clients and whether the client presently at his workstation, which can be determined by the level of activity at the client's workstation. The presence feature also allows clients to declare themselves unavailable to receive instant messages so that incoming messages can be blocked.

[0004] Because of the wide range of capabilities and the convenience of instant messaging, it is becoming a popular means of communication among clients on networks. For example, individual companies are using instant messaging utilities as their preferred means of communication among employees.

SUMMARY OF THE INVENTION

[0005] The present invention is directed to a system and method for combining the convenience of instant messaging with video conferencing capability to allow a user to initiate a video conference using IM. The system of the invention includes at least two client nodes which are adapted to communicate with each other via an instant messaging utility. An instant messaging server supports instant messages between the two client nodes. A second server supports video conferences between video conference participants. In accordance with the invention, a video conference is initiated between video conference participants in response to an instant message transmitted between the at least two client nodes.

[0006] The video conference participants can participate in the video conference by any of several possible communication modes. For example, a participant may participate in a video conference via a desktop computer or dedicated video conferencing system using a video conferencing standard protocol such as H.323 video conferencing protocol. The participants may communicate via the public switched telephone network (PSTN), cellular communication, and ISDN protocol or an ATM protocol. Each participant may communicate via one or more internet IP gateways which form the interface between the internet and a particular participant's communication mode.

[0007] In one embodiment, the instant message contains information used to identify the communication mode to be used by a participant in the video conference. That is, an IM client with IM capability can initiate a video conference using the IM utility to identify participants in a video conference. A database used in connection with initiating video conferences indexes and catalogs communication and/or contact data for each participant in the identified video conference. This information is used to set up the video conference among the identified participants using each participant's preferred communication mode. These communication modes can be any of those identified above. In one embodiment, another server is used to coordinate the video conference among the participants identified by the instant message. This third server, in conjunction with the database, contains all of the communication mode information mentioned above and tabulates the communication mode information with participants in each initiated video conference. This third server can receive communication mode information from the instant message used to initiate the video conference. The information can then be used by the third server to set up the video conference using the appropriate communication modes associated with the identified participants.

[0008] Hence, in accordance with the invention, the increasingly popular instant messaging utility implemented by many internet service providers (ISP) such as AOL, MSN, etc. can be used to automatically initiate a video conference. This can be a significant convenience to business and personal users compared to conventional systems in which one may have to visit a dedicated website to initiate a video conference.

BRIEF DESCRIPTION OF THE DRAWINGS

[0009] The foregoing and other objects, features and advantages of the invention will be apparent from the more particular description of preferred embodiments of the invention, as illustrated in the accompanying drawings in which like reference characters refer to the same parts throughout the different views. The drawings are not necessarily to scale, emphasis instead being placed upon illustrating the principles of the invention.

[0010]FIG. 1 contains a schematic block diagram illustrating one embodiment of the system of the invention in which an instant messaging utility is used to initiate and support a video conference.

[0011]FIGS. 2 and 3 are functional block diagrams and protocol diagrams, respectively, of initiation of a video conference in which a first instant messaging client invites a second instant messaging client to participate in the conference, in accordance with one embodiment of the invention.

[0012]FIGS. 4 and 5 are functional block diagrams and protocol diagrams, respectively, of initiation of a video conference in which a first client initiates the conference via a H.32× communication to an instant messaging client, in accordance with one embodiment of the invention.

[0013]FIG. 6 is a protocol diagram for the scenario in which IM users call H.32× users, in accordance with one embodiment of the invention.

[0014]FIG. 7 contains a functional block diagram of the operation of the invention with an IM client, in accordance with one embodiment of the invention.

[0015]FIG. 8 illustrates the event sequence between an IM client and a remote buddy who does not have the plugin, in accordance with one embodiment of the invention.

[0016]FIG. 9 illustrates the event sequence between two plugins, in accordance with one embodiment of the invention.

[0017]FIG. 10 contains a schematic functional block diagram of integrating the plugin of the invention with an 1M application using vendor APIs.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS OF THE INVENTION

[0018]FIG. 1 contains a schematic block diagram illustrating one embodiment of the system 10 of the invention in which an instant messaging utility is used to initiate and support a video conference. The system 10 is implemented over a network such as the Internet, and communication among the system components is via network protocol such as the Internet Protocol (IP) indicated by the solid lines with arrowheads in FIG. 1.

[0019] The system includes a number of clients 12 which are capable of communicating over the network by some conventional instant messaging (IM) utility. Each client 12 can be, for example, a computer adapted to communicate over the Internet. Each of the clients 12 includes an IM client software module 16 which permits the client 12 to send and receive instant messages. Each of the IM client modules 16 can create, transmit and receive instant messages. The IM utility is supported by a messenger service or IM server 14 on the network. An IM client 12/16 creates an instant message and forwards the message to the IM server 14. The IM server 14 analyzes the message and forwards it to its intended recipient IM client 12/16.

[0020] In accordance with the invention, the system 10 also provides the capability to perform video conferencing over the network, i.e., Internet. Video conferences among video conferencing (VC) clients 28 are initiated and supported by a video conferencing server 24, also referred to herein as a multipoint conferencing unit (MCU). The MCU can be of the type manufactured, sold and licensed by First Virtual Communications, Inc. of Nashua, New Hampshire and Santa Clara, Calif., the assignee of the present patent application. When a video conference is in session, the MCU 24 enables and manages the conference. The MCU 24 formats audio and video data from the clients 28 and sends the audio and/or video data to the clients 28 as participants in the conference. The MCU can receive and transmit the video conference data to and from the clients 28 using some standard video conferencing protocol, for example, H.323 protocol, T. 120 protocol, session initiation protocol (SIP) or CUseeMe protocol provided by First Virtual Communications, Inc., the present assignee.

[0021] As illustrated in FIG. 1, in general, the MCU 24 can support video conferences with VC clients 28 communicating by various means. For example, VC clients 28 can participate in a conference via the public switched telephone network (PSTN), or via an ISDN H.320 standard protocol, or an ATM H.321 standard protocol, or a cellular communication protocol, etc. To support each of these means of communication, the MCU 24 interfaces with such clients via a gateway 26 which provides an interface which translates between the protocol used by the VC client 28 participating in the video conference and the MCU 24 supporting the video conference. Also, the VC client 28D can communicate directly with the MCU 24 in a video conferencing protocol, eliminating the need for a gateway 26.

[0022] Conventionally, video conferences are initiated on the MCU 24 by one of the VC clients identifying the “invitees” or participants in a video conference such as by visiting a web page supported by the MCU 24. In response, the MCU 24 contacts each of the participants and sets up communication links with them or their associated gateways using a video conferencing protocol. When the conference begins, the MCU 24 transmits and receives conferencing data to and from the participating clients. The conference can be initiated using a server, referred to herein as a “click-to-meet” CTM server 20, which supports the web page at which the video conference is initiated by one of the VC clients identifying the participants. The CTM server 20 interfaces with a database 22 which stores the identities and contact information for all potential participants in a conference. The database 22 also stores the communication modes used by each participant. When the participants are identified, the server 20 uses the database 22 to set up the video conference using the communication modes for all of the identified participants.

[0023] In accordance with the invention, video conferences are initiated using the instant messaging utility. To that end, each IM client 12 includes a video conference module 18 which interfaces with both the IM client module 16 and the CTM server 20 to initiate a video conference. In accordance with the invention, the IM utility on each client 12 is modified to permit a client to identify invitees to a conference. These invitees can be, for example, taken from a buddy list supported by the IM utility. In one embodiment, a user at an IM client 12 can set up a video conference by clicking on one or more buddies in a buddy list provided by the IM utility.

[0024] The IM client module 16 and the video conference module 18 within each client 12 are interface to each other. When an instant message setting up a video conference is sent by a client 12 via its IM client module 16, the video conference module 18 detects the message. It extracts information from the message which is used to set up the video conference automatically through the CTM server 20. The information extracted from the IM can include the identity, address and communication mode for each prospective participant in the conference. Once the CTM server 20 receives this information, it can initiate the conference via the MCU 24. Alternatively, the information extracted from the instant message can include the identity of the prospective participants in the video conference. This identity information is provided to the CTM server 20 which can associate each participant with its address, communication mode, gateway address, and other required information, using the database 22. This information is used in setting up the video conference in the MCU 24.

[0025]FIG. 1 is a generalized block diagram which illustrates the general case of the invention, namely, one or more IM clients 12 being capable of automatically initiating a video conference among one or more video conferencing clients 28 using an IM utility. It will be understood, however, that in one likely configuration of the invention, the IM clients 12 are the same as the VC clients 28. For example, each IM client 12 can be a user's computer adapted to communicate on the Internet. The computer can have the IM client module 16 and the video conferencing client 18 installed. Also, the computer can include the video conferencing client module as well. In this configuration, the user can decide to initiate a video conference on his own computer. He can use his instant messaging facility to invite other participants. In response, the CTM server 20 and MCU 24 can initiate the video conference on the inviter's computer and with the other invited participants.

[0026] In general, the instant-message-initiated video conferencing capability of the invention is implemented in modules at the individual clients. For example, the clients 12 which initiate the conference via instant messages include both IM modules 16 responsible for sending and receiving instant messages and video conference initiation modules 18 which extract data from the instant messages to initiate the conferences, in accordance with the foregoing description. The video conferencing clients 28 include the actual video conferencing client modules which interface with the MCU 24 to present the video conference to the users at the clients 28. To participate in a video conference, the client 28 must have the video conference module installed. In the event that an invitee to a conference does not have the module installed, the client 28 is automatically directed to an installation center which provides the necessary modules in plug-in form via the Internet.

[0027] In accordance with the invention, the CTM server 20, in conjunction with the database 22, maintains the capability to initiate video conferences with the various VC clients 28. As noted above, the database 22 and CTM server 20 maintain information as to the modes of communication, e.g., telephone, cellular, etc., used by each client 28 such that, when a video conference is initiate, each client 28 can be contacted and connected to the conference by the correct communication mode. In accordance with the invention, the CTM server 20 also provides an additional capability in that it “advertises” or makes information available as to presence of the clients 28. That is, analogous to the method by which an instant messaging system advertises presence of individual IM clients on the network, the CTM server 20 in accordance with the invention advertises presence of individual VC clients 28. As noted above, these VC clients 28 may be colocated with corresponding IM clients 12, such as the case where a user's desktop computer contains an IM client software module 16, a video conference initiation software module 18 and a video conferencing client software module 28. As an example of the CTM server's capability to advertise presence of VC clients 28, the CTM server 20 may advertise that a particular client 28 is available to receive a cellular communication. Also, the CTM server 20 and database 22 may be set up, for example, to indicate a client 28 as being reachable by cellular communication when the clients' IM presence indicates that he is away from his computer. This presence feature is implemented via a link between the CTM server 20 and the IM server 14. As a result, IM clients 12 can know whether and by what means of communication particular clients 28 are available for conferencing.

[0028] In accordance with an embodiment of the invention, there are generally three methods of initiating a video conference. The messaging in each case is basically the same and is in accordance with the following description, but the endpoints, i.e., VC clients 28, may either call on to the conference or be invited into the conference. Any conference can be made up of either of these caller/callee types.

[0029] The first initiation method is referred to as desktop initiation. Instant messaging is used via menu choice, added buttons or other means of selection to identify participants. The caller initiates invitation through IM and launches either a local application (such as Microsoft NetMeeting or CUseeMe client software provided by First Virtual Communications, Inc., the present assignee), a web page with a plugin (such as CUseeMe Web plugin provided by First Virtual Communications, Inc.) or its own embedded audio/video technology, or is called on its local computer or separate device, e.g., telephone, dedicated room video conferencing system, etc.

[0030] The second method involves IM presence advertised by the CTM server 20. Presence of devices such as room systems, cellular phones, etc., is advertised by the CTM server on behalf of users available at cell phones, room systems, etc. In this case, instant messages may not be exchanged with the actual device used to participate in the conference.

[0031] In the third method, presence is advertised for an existing conference. For example, the existing conference, such as a regularly scheduled company meeting, is listed on an IM client 12 as a “Buddy.” The client 12 can join the conference simply by clicking on the buddy icon for the conference.

[0032] The following describes the modules at the clients used to initiate and support video conferences using the instant messaging utility, in accordance with the invention.

[0033] 1. Components

[0034] The components of the system of the invention which implements audio/video enhanced instant messaging and video conferencing initiated using the instant messaging system will now be described.

[0035] 1.1 Desktop Client

[0036] The desktop client has a user interface similar to that of a traditional instant messaging client such as MSN and iPulse. It has the standard instant messaging features of contact list and its management functions such as add/remove group/contact, and an icon in the Windows taskbar tray. In one embodiment, audio and video conferencing is integrated into the instant message and group conference scenarios for up to 4 participants. Once in a group conference, the creator of a conference may invite additional participants.

[0037] 1.1.1 Partner/OEM Friendly User Interface (UI)

[0038] The UI is adaptable to being provided as a component to an original equipment manufacturer (OEM) because it provides the customizations listed below. The implementation of these items provides the following features:

[0039] A. Pluggable Resources (Graphics)—The ability to easily at least partially change the “skin” of the application, with OEM specific graphics.

[0040] B. Ad Space (Standard) in client—Ad space is provided in industry standard format similar to AIM, with clickthrough support.

[0041] C. URL launched Web based Conference Pages—All text and A/V enhanced conferences can be launched in web pages instead of the typical application windows. Sample templates are provided for OEMs to add their own graphics. A default page is provided by if the OEM partner does not supply one.

[0042] 1.1.2. Installation

[0043] The application has a standard installer such as a standard Windows installer.

[0044] 1.2.4 IM Call Router

[0045] The back end component bridges the IM and A/V conferencing environments and controls management of connections in the A/V enhanced IM system. It is designed to support any IM system a well as any video conferencing protocol. The capabilities of the IM Call Router include the following.

[0046] A. Handle requests for calls from A/V enabled IM endpoints to other A/V enabled IM endpoints.

[0047] B. Handle incoming calls from videoconferencing environments such as session initiation protocol (SIP) and H.323, and map these requests to specific IM users.

[0048] C. Handle outgoing calls from A/V enabled IM clients to the same videoconferencing endpoints as item B.

[0049] D. Request A/V conferences and redirect the callers and callees to the appropriate conference.

[0050] The IM Call Router has the following components.

[0051] A. IM Plugin—Responsible for all communication with IM clients through the IM server.

[0052] B. Conference Allocator Plugin—Responsible for all communication between the IM router and the conference allocator.

[0053] C. Call Redirector Plugin—This component handles incoming and outgoing calls from/to other network protocols such as SIP and H.323 and is responsible for all communication between the IM Call Router and the non-IM endpoints.

[0054] Further details of the IM Call Router are described below.

[0055] 1.3. Smart Conference Allocator

[0056] The smart conference allocator is responsible for creating conferences in an application service provider (ASP) video conferencing environment. The ASP environment in accordance with the invention can be of the type described in copending U.S. patent application Ser. No. 09/735,828, filed on Dec. 13, 2000, entitled, “Application Service Provider Configuration and Method for a Conferencing Environment,” assigned to First Virtual Communications, Inc., the assignee of the present application. The contents of that application are incorporated herein in their entirety.

[0057] The ASP in this application also refers to a system configuration in which the system is installed into an enterprise which then deploys services only to its employees. This configuration is referred to herein as an enterprise internal deployment.

[0058]2. A/V Enhanced Instant Messaging Scenarios

[0059] There are two scenarios that are addressed in accordance with the invention. The two scenarios include IM users inviting other IM users to participate in a video conference and H.320standard protocol users calling IM users. For either scenario, the following items are provided in accordance with the invention.

[0060] A. An intelligent server side component (IM Call Router) to handle conferencing requests on behalf of IM clients and/or the Intelligent H.323 call router.

[0061] B. ASP components for dispatching incoming calls, dispatching and allocating conferences, and notifying the IM Call Router of certain events.

[0062] C. An additional channel between the IM clients, through the IM server to the IM Call Router to communicate A/V conference requests and information.

[0063] For all scenarios in this section, there are no client side APIs needed on the client side other than, for example, a CUseeMe Web software development kit (SDK) sold by First Virtual Communications, Inc. of Nashua, New Hampshire and Santa Clara, Calif. and the additional IM channels for communication between IM components. The intelligence for finding conferences and other users stays on the server side and is implemented in the IM Call Router.

[0064] The following sections describe the scenarios and components.

[0065] 2.1 IM user Invites IM user(s)

[0066] When one IM user invites another IM user into an A/V conference, a private communications channel is opened through the IM Server to the IM Call Router. The IM Call Router initiates a conference via the conference allocator, with the appropriate attributes determined by the capabilities of endpoints (determined from Presence info and IM DB Properties). Once the conference information (IP, conference ID, potentially other conference attributes) is determined, the conference dispatcher initiates the location and invitation of the user through IM Call Router. Eventually the IM Call Router will get the conference information to the invitee(s) of which conference to connect to, and the connection will be initiated by the client through the CUseeMe Web SDK. FIGS. 2 and 3 are component and protocol diagrams of this process.

[0067] 2.2 Incoming H.32× Calls to IM Users

[0068] In addition to IM users calling/conferencing with other IM users, an infrastructure for incoming and outgoing calls with h.32× systems is supported through the ASP and IM System. ASP components help map incoming h.32× calls to IM users, check their availability and through the IM system get them to meet the incoming caller in a conference allocated for an H.32× port. The mapping is done by additional destination h.32× alias information added to the initial call destination address to additional properties on user records in the IM database (i.e. E164 alias, H323 ID).

[0069]FIGS. 4 and 5 illustrate the components and protocol necessary to satisfy supporting incoming h.320 calls to IM users, with the added bonus of calls from other h.323 endpoints.

[0070] 2.3 Outgoing Calls to H.32× Users

[0071]FIG. 6 is a protocol diagram for the scenario in which IM users call H.32× users.

[0072] 2.4 Conference Registered as a Buddy

[0073] In this scenario, the backend components can register with the IM server a buddy or contact which is actually a conference, such that, when an IM endpoint initiates a message to that contact, the IM server can bring it into a video conference without any special software on the desktop, unless it is needed for the actual video conferencing. All the call routing and information is figured out by the backend servers in this case.

[0074] The following describes the interaction between the IM client and the IM Server in accordance with the invention. The messages passed between the IM client and the IM server in initiating a video conference in accordance with the invention are described.

[0075] 1. IM System Components

[0076] This section describes the system components in accordance with the invention.

[0077] 1.1 The IM Client

[0078] The IM Client is the software located at the client workstation. From a developer point of view this software has the following (low level) capabilities.

[0079] A. Exchange standard IM messages with the IM Server

[0080] B. Exchange custom IM messages with the IM Server

[0081] C. Establish a connection with the MCU

[0082] From a user point of view this software has the following (high level) capabilities.

[0083] A. All the standard IM features

[0084] B. Call another IM Client

[0085] C. Call a H323 Client

[0086] Examples IM Clients which can be used in connection with the invention include the IPulse application provided by Ericsson and Microsoft Windows XP Messenger. These can be used with the CUseeMe Web toolkit manufactured, sold and licensed by First Virtual Communications, Inc. of Nashua, N.H. and Santa Clara, Calif., which enables them to be audio and video capable. They can also be used with video capabilities included.

[0087] 1.2 The H323 Client

[0088] In one configuration of the system of the invention, the H323 Client is standard H323software able to establish a connection to another H323 end point via a GateKeeper.

[0089] 1.3 The H323 Gate Keeper

[0090] In one embodiment, the GateKeeper is a standard H323 GateKeeper able to communicate with the IM Server and the MCU.

[0091] 1.4 The MCU

[0092] In one embodiment, the MCU is an H323 Multipoint Conferencing Unit (MCU) of the type sold by First Virtual Communications, Inc., the assignee of the present application.

[0093] 1.5 The IM Server

[0094] In one embodiment, the IM Server is a piece of server software that is able to handle IM standard messages, some custom messages, and is also able to communicate with the call router and the GateKeeper. The IM Server software can be, for example, the IPulse server and some extension to it. Other examples of IM servers which can be used in connection with the invention include the Microsoft MSN and Exchange Servers.

[0095] 2. Calling Scenarios

[0096] The following tables define the different calling scenarios that are supported by the IM System in accordance with the invention. TABLE 1 Case 1: The Called party is not Connected. IM Caller IM Server IM Called Party Send a call request to the IM Server Reply that the Callee is not connected Call terminated

[0097] TABLE 2 Case 2: The Called party is connected but refuses the call. IM Caller IM Server IM Called Party Send a call request to the IM Server Forward the call to the IM Called party The Client is ringing The Client rejects the call Tell the IM Server that the call was rejected by the user Forward the call rejection to the IM Caller Call terminated

[0098] TABLE 3 Case 3: The Called party is connected and accepts the call. IM Caller IM Server IM Called Party Send a call request to the IM Server Forward the call to the IM Called The Client is ringing The Client accepts the call Tell the IM Server that the user accepted the call. Create the conference. Send the conference address to both ends. Connect to the conference. Connect to the conference.

[0099] TABLE 4 Case 4: The Caller cancels the call while it rings. IM Caller IM Server IM Called Send a call request to the IM Server Forward the call to the IM Called The Client is ringing The Client tells the IM server that the user cancelled the call Forward the cancellation to the client. Call Terminated.

[0100] Parameters used in communication between the IM Caller (IM Client) and IM Server include the following.

[0101] iConference: ConfAddress

[0102] The iConference parameter contains the address of the conference the IM Client should connect to. The ConfAddress contains an IP address and an MPCS conference ID.

[0103] iSettings: ConfSettings

[0104] The iSettings parameter contains the parameters the IM Client should use to connect to the conference. A typical setting indicates the ability or inability of the client to send video.

[0105] 3. Messages

[0106] This section describes messages sent by the Client to the Server.

[0107] 3.1 Create Call

[0108] This message is sent by the caller client to the server when it wants to start a call. This is the only synchronous message, all other messages are asynchronous an do not return anything.

[0109] Parameters:

[0110] iAddress: URL

[0111] The iAddress parameter contains the address of the other end point to call.

[0112] Reply:

[0113] oError: Integer

[0114] The oError return value contains the error code of the request.

[0115] Possible error codes are:

[0116] ERR_NO_ERROR

[0117] The Call was successfully created.

[0118] ERR_NOT_ALLOWED

[0119] The IM Client is not allowed to create a call.

[0120] ERR_BAD_ADDRESS

[0121] The IM Server does not recognize the address.

[0122] oCallRef: Call Reference

[0123] If the call was successfully created, oCallRef contains the address of the other end point to call. This reference is used by all other messages and remains valid until the call is terminated.

[0124] 3.2 Incoming Call

[0125] This message is sent by the server to the called client after a call was created.

[0126] Parameters:

[0127] iCallRef: Call Reference

[0128] The iCallRef parameter contains the unique reference to the call.

[0129] iCaller: URL (optional)

[0130] The iCaller parameter contains the address of the caller client.

[0131] 3.3 Terminated Call

[0132] This message is sent by any client to the server when it cancels a pending call. The server also forwards this message to the other client. The Server itself can decide to send this message on its own. After this message the Call Reference is no longer valid

[0133] The IM call router will now be described in detail. The purpose of the IM Call Router is to let standard video conferencing clients, such as H.323, SIP, and CUseeMe protocol (manufactured, sold and licensed by First Virtual Communications, Inc., the present assignee) clients, call IM clients via a conference call hosted on a video conferencing server such as an MCU.

[0134] 1. Architecture

[0135] The IM call router supports multiple IM systems and multiple video conferencing systems. In order to achieve this goal the IM call router has an extensible architecture that supports plugins.

[0136] The following sections describe the different types of plugins supported by the IM call router.

[0137] 1.1 The Call Redirector Plugin

[0138] The call redirector plugin provides an interface for video conferencing systems. It tells the IM call router that a call occurred, and then forwards the call status returned by the router to the video conferencing client. An IM call router may use multiple call redirector plugins simultaneously. The IM redirector plugin can be compatible with H323, SIP or CUseeMe protocols.

[0139] 1.2 The IM Plugin

[0140] The IM plugin provides an interface for IM systems. It forwards the call received from the call redirector to the IM client, then returns the call status returned by the IM client to the IM call router. An IM call router may use multiple IM plugins simultaneously. The IM plugin can be Microsoft Windows Messenger IM, Ipulse, ICQ or AIM.

[0141] 1.3 The Conference Allocator Plugin

[0142] The conference allocator plugin creates a video conference on the video conference server (MCU) that will host the IM client/video conferencing client session. An IM call router uses only one allocator plugin.

[0143] In one embodiment, the conference allocator may open a telnet connection with a video conferencing server. In another embodiment, the conference allocator performs load balancing, using a cloud of video conferencing servers.

[0144] 2. Plugins, APIs and Callbacks

[0145] This section describes the APIs and callbacks that are implemented by the plugins. Because the IM call router may handle a lot of simultaneous calls, because it is time critical, and because some APIs may require user interaction, all the APIs are asynchronous, and none of them requires a reply.

[0146] 2.1 Call Redirector IM Router Messages

[0147] This section describes messages sent by the call redirector plugin to the IM router.

[0148] 2.1.1 CallStarted

[0149] This message is sent by the call redirector when it receives a call. The call is then maintained in “ringing” mode until the IM router accepts or rejects the call.

[0150] Parameters:

[0151] iCallRef: String

[0152] The iCallRef parameter is a string that contains a unique reference to the call. This reference is used by all the other messages and remains valid until the call is terminated.

[0153] iAddress: IMAddress

[0154] The iAddress parameter contains the address of the IM client. The IMAddress type is a string.

[0155] 2.1.2 CallCanceled

[0156] This message is sent by the plugin when the video conferencing client cancels a pending call.

[0157] Parameters:

[0158] iCallRef: String

[0159] The iCallRef parameter contains the unique reference to the call. This reference is the same as the one passed to the CallStarted message.

[0160] 2.2 IM Router to Call Redirector Messages

[0161] This section describes messages sent by the IM router to the call redirector plugin. 2.2.1 CallRejected

[0162] This message is sent by the IM router in response to a CallStarted message when the call cannot be issued. This message terminates the call process, then the call reference is no longer valid.

[0163] Parameters:

[0164] iCallRef: String

[0165] The iCallRef parameter contains the unique reference to the call. This reference is the same as the one passed to the CallStarted message.

[0166] iError: Integer

[0167] The iError parameter contains the reason why the call was rejected.

[0168] Possible error codes are:

[0169] ERR_NOT_VALID

[0170] The iAddress parameter passed to the CallStart message is not reconized by any IM plugin.

[0171] ERR_NOT_FOUND

[0172] The IM Client described in the iAddress parameter passed to the CallStart message was not found.

[0173] ERR_NOT_CONNECTED

[0174] The IM Client is offline.

[0175] ERR_BUSY

[0176] The IM Client is busy.

[0177] ERR_REJECTED

[0178] The IM Client refused the call.

[0179] ERR_TIMEOUT

[0180] The IM Client did not answer the call.

[0181] 2.2.2 CallAccepted

[0182] This message is sent by the IM router in response to a CallStart message when the call is accepted.

[0183] Parameters:

[0184] iCallRef: String

[0185] The iCallRef parameter contains the unique reference to the call. This reference is the same as the one passed to the CallStarted message.

[0186] iConfIP: String

[0187] The iConfIP parameter contains the IP address of the video conferencing server (MCU) that will host the conference.

[0188] iConfID: Integer

[0189] The iConfID parameter contains the ID of the conference.

[0190] 2.3 IM Router To IM Plugin Messages

[0191] This section describes messages sent by the IM router to the IM plugin.

[0192] 2.3.1 CallStarted

[0193] This message is sent by the IM router when in receives an incoming call notification from the call redirector. When receiving this message, the IM plugin resolves the IM client address, checks if the IM Client exists and is connected, and, if so, forwards the call request to the IM client, which will then pop up an “Incoming Call” dialog.

[0194] Parameters:

[0195] iCallRef: Interger

[0196] The iCallRef parameter contains a unique reference to the call. This reference is used by all the other messages and remains valid until the call is terminated.

[0197] iAddress: IMAddress

[0198] The iAddress parameter contains the address of the IM client. The IMAddress type is a string.

[0199] 2.3.2 CallCanceled

[0200] This message is sent by the IM router when it receives a call cancelled notification from the call redirector. The IM plugin then forwards this notification to the IM client which will close the “Incoming Call” Dialog.

[0201] Parameters:

[0202] iCallRef: Integer

[0203] The iCallRef parameter contains the unique reference to the call. This reference is the same as the one passed to the CallStarted message.

[0204] 2.4 IM Plugin To IM Router Messages

[0205] This section describes messages sent by the IM plugin to the IM router.

[0206] 2.4.1 CallRejected

[0207] This message is sent by the IM plugin in response to a CallStarted message when the call cannot be issued. This message terminates the call process, then the call reference is no longer valid.

[0208] Parameters:

[0209] iCallRef: Integer

[0210] The iCallRef parameter contains the unique reference to the call. This reference is the same as the one passed to the CallStarted message.

[0211] iError: Integer

[0212] The iError parameter contains the reason why the call was rejected.

[0213] Possible error codes are:

[0214] ERR_NOT_VALID

[0215] The iAddress parameter passed to the CallStart message is not recognized by any IM plugin When the IM router receives this error code it attempts to use another IM plugin to resolve the address. If all the available IM plugins return this error code, the error is forwarded to the Call Redirector.

[0216] ERR_NOT_FOUND

[0217] The IM Client described in the iAddress parameter passed to the CallStart message was not found.

[0218] ERR_NOT_CONNECTED

[0219] The IM Client is offline.

[0220] ERR_BUSY

[0221] The IM Client is busy.

[0222] ERR_REJECTED

[0223] The IM Client refused the call.

[0224] ERR_TIMEOUT

[0225] The IM Client didn't answer the call.

[0226] 2.4.2 CallAccepted

[0227] This message is sent by the IM plugin in response to a CallStart message when the call is accepted. When the IM router receives this call it asks the conference allocator to create a conference then forwards the acceptance to the call redirector with the newly created conference address.

[0228] Parameters:

[0229] iCallRef Integer

[0230] The iCallRef parameter contains the unique reference to the call. This reference is the same as the one passed to the CallStarted message.

[0231] 2.5 IM Router To Conference Allocator Messages

[0232] This section describes the message sent by the IM router to the conference allocator.

[0233] 2.5.1 CreateConf

[0234] This message is sent by the IM router when the IM client accepted an incoming call.

[0235] Parameters:

[0236] iRequestRef: Integer

[0237] The iRequestRef parameter is a unique reference that will help the IM router to identify (Alf, please complete this sentence.)

[0238] iConfSettings: ConfSettings

[0239] The iConfSettings parameter contains information about the conference.

[0240] 2.6 Conference Allocator to IM Router Messages

[0241] This section describes messages sent by the conference allocator to the IM router.

[0242] 2.6.1 ConfCreated

[0243] This message is sent by the conference allocator to tell the IM router that the conference was successfully created.

[0244] Parameters:

[0245] iRequestRef: Integer

[0246] The iRequestRef parameter is the unique request reference. This reference is the same as the one passed to the CreateConf message.

[0247] iConfIP: String

[0248] The iConfIP parameter contains the IP address of the video conferencing server (MCU) that will host the conference.

[0249] iConfID: Integer

[0250] The iConfID parameter contains the ID of the conference.

[0251] 2.6.2 Failed

[0252] This message is sent by the conference allocator to tell the IM router that it was not able to create a conference.

[0253] Parameters:

[0254] iRequestRef: Integer

[0255] The iRequestRef parameter is the unique request reference. This reference is the same as the one passed to the CreateConf message.

[0256] iError: Integer

[0257] The iError parameter contains the ID of error that prevent the conference allocator to create the conference.

[0258] The IM plugin for IM systems in accordance with embodiments of the invention will now be described in detail. The plugin in accordance with the invention allows IM users to add video/audio capabilities to their IM client. It not only uses the user status and location features of

[0259] IM systems, but it also works together with the IN service.

[0260] The IM plugin is composed of two distinct conceptual modules even if both can fit into one executable. The back-end application manages the low-level layer of the IM protocol and IM plugin user interface on the IM application's user interface. The conference room application uses CUseeMe Web technology, manufactured, sold and licensed by First Virtual Communications, Inc., the present assignee, to display the video window.

[0261] The IM plugin in accordance with the invention is normally launched at system startup and runs in the background as an invisible application. A tray icon may be provided when the IM application is online if needed.

[0262] In accordance with the invention, there are two approaches to integrating the plugin of the invention with a third party IM application. The first involves using a local proxy to monitor any IM protocol messages as well as send custom/private messages used for conference rendezvous information, when no APIs are provided by the IM application vendor. The second involves using the vendor-supplied APIs to monitor IM events and messages as well as send custom/private messages for conference rendezvous information. These may be done at either caller and/or callee, or only at the sever to invite endpoints like Windows XP Messenger, which has a rendezvous protocol embedded. These two approaches are now described in detail.

[0263]1. The Proxy

[0264] During installation, the proxy is inserted between the client and the IM server. The IM plugin of the invention changes the IM application's connection settings to use a port on the local machine, where the proxy is listening. A solution with a real Socks proxy can also be implemented, changing the IM application's proxy settings instead of the IM server address itself.

[0265] The proxy decodes the IM protocol. It is able to retrieve information on the buddies like IM ID, IP address, and status. IM data is forwarded to the IM server/IM client.

[0266]FIG. 7 contains a functional block diagram of the operation of the invention with an existing third-party client. Incoming messages from other buddies are inspected and sometimes trapped in case of plugin-specific messages. Those messages can pass through the server, or come from a direct TCP connection with the buddies. Outgoing messages are intercepted as well, allowing introduction of custom information inside the messages, which are then forwarded to the IM server.

[0267] The plugin module is responsible for the integration of custom controls inside the third party IM application's user interface that let the user start video connections. A click on the video button can trigger, for example, a CUseeMe Web invitation to the remote chatter. Windows hooks are installed in the IM applications in order to receive video buttons events as well as hooks on windows creations to check which IM or chat window is visible.

[0268] The conference room in which the video conference takes place may or may not be an independent window, and by default it does not stick to the IM windows. The video is an autonomous communication tool, like chat or IM. Shortcuts are provided from within the IM window or the IM plugin UI, but if the IM window is closed, the video conference may persist.

[0269] Two different layouts are provided, and a setting allows the user to switch between the layouts. The ConfRoom is a singleton resource, as long as a video conference is in progress, all the video shortcuts in all the IM windows are grayed. An option allows the user to stick its video if that mode is preferred. CUseeMe for IPulse is an example of this kind of integration and an example of configurable layout.

[0270]FIG. 8 illustrates the event sequence between the IM plugin in accordance with the invention and a remote buddy who does not have the plugin. Back-end Local represents the interception of the IM protocol. The user interface on the local side contains the plugin buttons, IM client is the remote IM client and remote IM UI is the IM application's IM window. If the plugin download and installation are fast enough, the callee might call back the caller before the timeout.

[0271]FIG. 9 illustrates the event sequence between two plugins. Back-end Local and Back-end remote represent the interception of the IM protocol. IM plugin UI on both sides contains the plugin buttons.

[0272]2. Application APIs

[0273] This approach operates in an analogous fashion to the proxy and plugin described above. But, instead of intercepting messages with a proxy, the vendor has supplied APIs for a clean integration into its IM product. The plugin of the invention can register for events and query presence information of buddies in the list. The plugin can also create new message channels for communicating conference rendezvous information between endpoints, as well as intercept messages upon receipt. In addition, the application may also provide APIs such that the plugin of the invention can add menu choices and/or buttons to the IM application's user interface. Otherwise, the actual message content, sequence and parameters are the same as those used in the proxy approach. FIG. 10 is a schematic block diagram illustrating the API approach.

[0274] While this invention has been particularly shown and described with references to preferred embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made herein without departing from the spirit and scope of the invention as defined by the following claims. 

1. A system comprising: at least two client nodes adapted to communicate with each other via an instant messaging utility; an instant messaging server for supporting instant messages between the two client nodes; and a second server for supporting video conferences between video conference participants, a video conference being initiated between video conference participants in response to an instant message transmitted between the at least two client nodes.
 2. The system of claim 1, wherein at least one of the video conference participants participates in the video conference via the public switched telephone network (PSTN).
 3. The system of claim 1, wherein at least one of the video conference participants participates in the video conference via cellular communication.
 4. The system of claim 1, wherein at least one of the video conference participants participates in the video conference via a computer.
 5. The system of claim 1, wherein at least one of the video conference participants participates in the video conference via a network gateway.
 6. The system of claim 1, wherein at least one of the video conference participants participates in the video conference via a video conferencing standard protocol.
 7. The system of claim 1, wherein at least one of the video conference participants participates in the video conference via an ISDN standard protocol.
 8. The system of claim 1, wherein at least one of the video conference participants participates in the video conference via an ATM standard protocol.
 9. The system of claim 1, wherein the instant message contains information related to communication modes of the participants to be used by the participants to participate in the video conference.
 10. The system of claim 9, wherein the communication modes comprise communication via the public switched telephone network (PSTN).
 11. The system of claim 9, wherein the communication modes comprise cellular communication.
 12. The system of claim 9, wherein the communication modes comprise communication via a computer.
 13. The system of claim 9, wherein the communication modes comprise communication via a gateway.
 14. The system of claim 9, wherein the communication modes comprise communication via a video conferencing standard protocol.
 15. The system of claim 9, wherein the communication modes comprise communication via an ISDN standard protocol.
 16. The system of claim 9, wherein the communication modes comprise communication via an ATM standard protocol.
 17. The system of claim 1, further comprising a third server for processing information related to the participants in the video conference to initiate the video conference.
 18. The system of claim 17, wherein the third server receives the information from the instant message.
 19. The system of claim 17, wherein the information is related to communication modes of the participants to be used by the participants to participate in the video conference.
 20. The system of claim 19, wherein the communication modes comprise communication via the public switched telephone network (PSTN).
 21. The system of claim 19, wherein the communication modes comprise cellular communication.
 22. The system of claim 19, wherein the communication modes comprise communication via a computer.
 23. The system of claim 19, wherein the communication modes comprise communication via a gateway.
 24. The system of claim 19, wherein the communication modes comprise communication via a video conferencing standard protocol.
 25. The system of claim 19, wherein the communication modes comprise communication via an ISDN standard protocol.
 26. The system of claim 19, wherein the communication modes comprise communication via an ATM standard protocol.
 27. The system of claim 1, wherein the second server is a network video conferencing server which supports video conferences using a network video conferencing protocol.
 28. A communication method comprising: providing at least two client nodes adapted to communicate with each other via an instant messaging utility; providing an instant messaging server for supporting instant messages between the two client nodes; and providing a second server for supporting video conferences between video conference participants, a video conference being initiated between video conference participants in response to an instant message transmitted between the at least two client nodes.
 29. The method of claim 28, wherein at least one of the video conference participants participates in the video conference via the public switched telephone network (PSTN).
 30. The method of claim 28, wherein at least one of the video conference participants participates in the video conference via cellular communication.
 31. The method of claim 28, wherein at least one of the video conference participants participates in the video conference via a computer.
 32. The method of claim 28, wherein at least one of the video conference participants participates in the video conference via a network gateway.
 33. The method of claim 28, wherein at least one of the video conference participants participates in the video conference via a video conferencing standard protocol.
 34. The method of claim 28, wherein at least one of the video conference participants participates in the video conference via an ISDN standard protocol.
 35. The method of claim 28, wherein at least one of the video conference participants participates in the video conference via an ATM standard protocol.
 36. The method of claim 28, wherein the instant message contains information related to communication modes of the participants to be used by the participants to participate in the video conference.
 37. The method of claim 36, wherein the communication modes comprise communication via the public switched telephone network (PSTN).
 38. The method of claim 36, wherein the communication modes comprise cellular communication.
 39. The method of claim 36, wherein the communication modes comprise communication via a computer.
 40. The method of claim 36, wherein the communication modes comprise communication via a gateway.
 41. The method of claim 36, wherein the communication modes comprise communication via a video conferencing standard protocol.
 42. The method of claim 36, wherein the communication modes comprise communication via an ISDN standard protocol.
 43. The method of claim 36, wherein the communication modes comprise communication via an ATM standard protocol.
 44. The method of claim 28, further comprising providing a third server for processing information related to the participants in the video conference to initiate the video conference.
 45. The method of claim 44, wherein the third server receives the information from the instant message.
 46. The method of claim 44, wherein the information is related to communication modes of the participants to be used by the participants to participate in the video conference.
 47. The method of claim 46, wherein the communication modes comprise communication via the public switched telephone network (PSTN).
 48. The method of claim 46, wherein the communication modes comprise cellular communication.
 49. The method of claim 46, wherein the communication modes comprise communication via a computer.
 50. The method of claim 46, wherein the communication modes comprise communication via a gateway.
 51. The method of claim 46, wherein the communication modes comprise communication via a video conferencing standard protocol.
 52. The method of claim 46, wherein the communication modes comprise communication via an ISDN standard protocol.
 53. The method of claim 46, wherein the communication modes comprise communication via an ATM standard protocol.
 54. The method of claim 28, wherein the second server is a network video conferencing server which supports video conferences using a network video conferencing protocol. 